You should read the simple examples before trying these more advanced ones.
HINT: use right Amiga C the drag then clip the examples out of these docs to avoid typos.
A word of caution. NEVER try to read from both ends of the pipe at the same time. If you 'type awnpipe:mypipe1' in two separate shells both will hang waiting for data to come from the pipe.
If this happens to you during testing open the pipe a third time adding '/a' to the pipename 'type awnpipe:mypipe/a'. this causes the pending reads to abort and the deadlock (hang) ends.
---
It is possible to tap into or duplicate the data passed in a pipe. '/t' will add a readonly third end to a pipe.
Make sure you have two different shells available.
In the first shell type 'type awnpipe:mypipe/t'
In the second shell type 'echo >awnpipe:mypipe hello'
In the second shell type 'type >awnpipe:mypipe '
The word hello came back from both the second end of the pipe and the 'Tap' third end.
---
In the first shell type 'copy con:////pipe-test/close awnpipe:mypipe'
In the second shell type 'type >awnpipe:mypipe '
Type a few lines of text into the test con:, not nothing comes out in the second shell. Close the test con:, now the data comes out. This is because the type command wants to read large blocks of data.
'/i' will cause data to pass out of the pipe immediately (as soon as its available).
In the first shell type 'copy con:////pipe-test/close awnpipe:mypipe'
In the second shell type 'type >awnpipe:mypipe/i '
Now the text comes out of the pipe each time you hit return in the test con:.
Close the test con: to end the example.
---
You can use AWNPipe to read the tooltypes of an icon. The second end of the pipe automatically reads the tooltypes of FILENAME when '/xiFILENAME' is used. NOTE that parameters that start with '/x' can not be mixed with other parameters!
In a shell type 'type awnpipe:mypipe/xiDevs:dosdrivers/awnpipe'
YES the pipe name contains two colons ':', don't let it bug you.
The tooltype information from Devs:dosdrivers/awnpipe prints out. Note you do not include '.info' in the file name.
---
AWNPipe can be used to test pattern matching of text. '/xm' is used for pattern matching. Data is usually written into the pipe, and the results of the pattern matching read back from THE SAME END OF THE PIPE. The second end of the pipe is automatically connected to a task that is doing the pattern matching. '/xmrFILENAME' causes the data to be read from a file rather than the pipe, the match results are read from the pipe.
In a shell type 'type awnpipe:mypipe/xmrcon:////pipetest/close'
In the pipetest con: type '#?.' . This sets a pattern to match to. 'ok 1' should come back from the pipe. ('ok 0' would means you did not enter a pattern so an exact match of the text will be tested for.)
In the pipetest con: enter some text. If the text ends with '.' then the pipe responds with '1' meaning a match. If not the pipe responds with '0' meaning no match. Close the pipe test con: to end the example.
